SGI Freeware 1999 August

home *** CD-ROM | disk | FTP | other *** search

/ SGI Freeware 1999 August / SGI Freeware 1999 August.iso / dist / fw_xemacs.idb / usr / freeware / lib / xemacs-20.4 / info / xemacs.info-9.z / xemacs.info-9

Wrap

GNU Info File | 1998-05-21 | 48.2 KB | 1,171 lines

This is Info file ../../info/xemacs.info, produced by Makeinfo version 1.68 from the input file xemacs.texi. This file documents the XEmacs editor. Copyright (C) 1985, 1986, 1988 Richard M. Stallman. Copyright (C) 1991, 1992, 1993, 1994 Lucid, Inc. Copyright (C) 1993, 1994 Sun Microsystems, Inc. Copyright (C) 1995 Amdahl Corporation. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the sections entitled "The GNU Manifesto", "Distribution" and "GNU General Public License" are included exactly as in the original, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that the sections entitled "The GNU Manifesto", "Distribution" and "GNU General Public License" may be included in a translation approved by the author instead of in the original English. File: xemacs.info, Node: Just Spaces, Prev: Tab Stops, Up: Indentation Tabs vs. Spaces =============== Emacs normally uses both tabs and spaces to indent lines. If you prefer, all indentation can be made from spaces only. To request this, set `indent-tabs-mode' to `nil'. This is a per-buffer variable; altering the variable affects only the current buffer, but there is a default value which you can change as well. *Note Locals::. There are also commands to convert tabs to spaces or vice versa, always preserving the columns of all non-blank text. `M-x tabify' scans the region for sequences of spaces, and converts sequences of at least three spaces to tabs if that is possible without changing indentation. `M-x untabify' changes all tabs in the region to corresponding numbers of spaces. File: xemacs.info, Node: Text, Next: Programs, Prev: Indentation, Up: Top Commands for Human Languages **************************** The term "text" has two widespread meanings in our area of the computer field. One is data that is a sequence of characters. In this sense of the word any file that you edit with Emacs is text. The other meaning is more restrictive: a sequence of characters in a human language for humans to read (possibly after processing by a text formatter), as opposed to a program or commands for a program. Human languages have syntactic and stylistic conventions that editor commands should support or use to advantage: conventions involving words, sentences, paragraphs, and capital letters. This chapter describes Emacs commands for all these things. There are also commands for "filling", or rearranging paragraphs into lines of approximately equal length. The commands for moving over and killing words, sentences, and paragraphs, while intended primarily for editing text, are also often useful for editing programs. Emacs has several major modes for editing human language text. If a file contains plain text, use Text mode, which customizes Emacs in small ways for the syntactic conventions of text. For text which contains embedded commands for text formatters, Emacs has other major modes, each for a particular text formatter. Thus, for input to TeX, you can use TeX mode; for input to nroff, Nroff mode. * Menu: * Text Mode:: The major modes for editing text files. * Nroff Mode:: The major mode for editing input to the formatter nroff. * TeX Mode:: The major modes for editing input to the formatter TeX. * Outline Mode:: The major mode for editing outlines. * Words:: Moving over and killing words. * Sentences:: Moving over and killing sentences. * Paragraphs:: Moving over paragraphs. * Pages:: Moving over pages. * Filling:: Filling or justifying text * Case:: Changing the case of text File: xemacs.info, Node: Text Mode, Next: Words, Prev: Text, Up: Text Text Mode ========= You should use Text mode--rather than Fundamental or Lisp mode--to edit files of text in a human language. Invoke `M-x text-mode' to enter Text mode. In Text mode, <TAB> runs the function `tab-to-tab-stop', which allows you to use arbitrary tab stops set with `M-x edit-tab-stops' (*note Tab Stops::.). Features concerned with comments in programs are turned off unless they are explicitly invoked. The syntax table is changed so that periods are not considered part of a word, while apostrophes, backspaces and underlines are. A similar variant mode is Indented Text mode, intended for editing text in which most lines are indented. This mode defines <TAB> to run `indent-relative' (*note Indentation::.), and makes Auto Fill indent the lines it creates. As a result, a line made by Auto Filling, or by <LFD>, is normally indented just like the previous line. Use `M-x indented-text-mode' to select this mode. Entering Text mode or Indented Text mode calls the value of the variable `text-mode-hook' with no arguments, if that value exists and is not `nil'. This value is also called when modes related to Text mode are entered; this includes Nroff mode, TeX mode, Outline mode, and Mail mode. Your hook can look at the value of `major-mode' to see which of these modes is actually being entered. Two modes similar to Text mode are of use for editing text that is to be passed through a text formatter before achieving its final readable form. * Menu: * Nroff Mode:: The major mode for editing input to the formatter nroff. * TeX Mode:: The major modes for editing input to the formatter TeX. Another similar mode is used for editing outlines. It allows you to view the text at various levels of detail. You can view either the outline headings alone or both headings and text; you can also hide some of the headings at lower levels from view to make the high level structure more visible. * Outline Mode:: The major mode for editing outlines. File: xemacs.info, Node: Nroff Mode, Next: TeX Mode, Prev: Text Mode, Up: Text Mode Nroff Mode ---------- Nroff mode is a mode like Text mode but modified to handle nroff commands present in the text. Invoke `M-x nroff-mode' to enter this mode. Nroff mode differs from Text mode in only a few ways. All nroff command lines are considered paragraph separators, so that filling never garbles the nroff commands. Pages are separated by `.bp' commands. Comments start with backslash-doublequote. There are also three special commands that are not available in Text mode: `M-n' Move to the beginning of the next line that isn't an nroff command (`forward-text-line'). An argument is a repeat count. `M-p' Like `M-n' but move up (`backward-text-line'). `M-?' Prints in the echo area the number of text lines (lines that are not nroff commands) in the region (`count-text-lines'). The other feature of Nroff mode is Electric Nroff newline mode. This is a minor mode that you can turn on or off with `M-x electric-nroff-mode' (*note Minor Modes::.). When the mode is on and you use <RET> to end a line containing an nroff command that opens a kind of grouping, Emacs automatically inserts the matching nroff command to close that grouping on the following line. For example, if you are at the beginning of a line and type `.(b <RET>', the matching command `.)b' will be inserted on a new line following point. Entering Nroff mode calls the value of the variable `text-mode-hook' with no arguments, if that value exists and is not `nil'; then it does the same with the variable `nroff-mode-hook'. File: xemacs.info, Node: TeX Mode, Next: Outline Mode, Prev: Nroff Mode, Up: Text Mode TeX Mode -------- TeX is a powerful text formatter written by Donald Knuth; like GNU Emacs, it is free. LaTeX is a simplified input format for TeX, implemented by TeX macros. It is part of TeX. Emacs has a special TeX mode for editing TeX input files. It provides facilities for checking the balance of delimiters and for invoking TeX on all or part of the file. TeX mode has two variants, Plain TeX mode and LaTeX mode, which are two distinct major modes that differ only slightly. These modes are designed for editing the two different input formats. The command `M-x tex-mode' looks at the contents of a buffer to determine whether it appears to be LaTeX input or not; it then selects the appropriate mode. If it can't tell which is right (e.g., the buffer is empty), the variable `tex-default-mode' controls which mode is used. The commands `M-x plain-tex-mode' and `M-x latex-mode' explicitly select one of the variants of TeX mode. Use these commands when `M-x tex-mode' does not guess right. * Menu: * Editing: TeX Editing. Special commands for editing in TeX mode. * Printing: TeX Print. Commands for printing part of a file with TeX. TeX for Unix systems can be obtained from the University of Washington for a distribution fee. To order a full distribution, send $140.00 for a 1/2 inch 9-track tape, $165.00 for two 4-track 1/4 inch cartridge tapes (foreign sites $150.00, for 1/2 inch, $175.00 for 1/4 inch, to cover the extra postage) payable to the University of Washington to: The Director Northwest Computer Support Group, DW-10 University of Washington Seattle, Washington 98195 Purchase orders are acceptable, but there is an extra charge of $10.00 to pay for processing charges. (The total cost comes to $150 for domestic sites, $175 for foreign sites). The normal distribution is a tar tape, blocked 20, 1600 bpi, on an industry standard 2400 foot half-inch reel. The physical format for the 1/4 inch streamer cartridges uses QIC-11, 8000 bpi, 4-track serpentine recording for the SUN. Also, SystemV tapes can be written in cpio format, blocked 5120 bytes, ASCII headers. File: xemacs.info, Node: TeX Editing, Next: TeX Print, Prev: TeX Mode, Up: TeX Mode TeX Editing Commands .................... Here are the special commands provided in TeX mode for editing the text of the file. `"' Insert, according to context, either ```' or `"' or `''' (`TeX-insert-quote'). `<LFD>' Insert a paragraph break (two newlines) and check the previous paragraph for unbalanced braces or dollar signs (`tex-terminate- paragraph'). `M-x validate-tex-buffer' Check each paragraph in the buffer for unbalanced braces or dollar signs. `C-c {' Insert `{}' and position point between them (`tex-insert-braces'). `C-c }' Move forward past the next unmatched close brace (`up-list'). `C-c C-e' Close a block for LaTeX (`tex-close-latex-block'). In TeX, the character `"' is not normally used; you use ```' to start a quotation and `''' to end one. TeX mode defines the key `"' to insert ```' after whitespace or an open brace, `"' after a backslash, or `''' otherwise. This is done by the command `tex-insert-quote'. If you need the character `"' itself in unusual contexts, use `C-q' to insert it. Also, `"' with a numeric argument always inserts that number of `"' characters. In TeX mode, `$' has a special syntax code which attempts to understand the way TeX math mode delimiters match. When you insert a `$' that is meant to exit math mode, the position of the matching `$' that entered math mode is displayed for a second. This is the same feature that displays the open brace that matches a close brace that is inserted. However, there is no way to tell whether a `$' enters math mode or leaves it; so when you insert a `$' that enters math mode, the previous `$' position is shown as if it were a match, even though they are actually unrelated. If you prefer to keep braces balanced at all times, you can use `C-c {' (`tex-insert-braces') to insert a pair of braces. It leaves point between the two braces so you can insert the text that belongs inside. Afterward, use the command `C-c }' (`up-list') to move forward past the close brace. There are two commands for checking the matching of braces. <LFD> (`tex-terminate-paragraph') checks the paragraph before point, and inserts two newlines to start a new paragraph. It prints a message in the echo area if any mismatch is found. `M-x validate-tex-buffer' checks the entire buffer, paragraph by paragraph. When it finds a paragraph that contains a mismatch, it displays point at the beginning of the paragraph for a few seconds and pushes a mark at that spot. Scanning continues until the whole buffer has been checked or until you type another key. The positions of the last several paragraphs with mismatches can be found in the mark ring (*note Mark Ring::.). Note that square brackets and parentheses, not just braces, are matched in TeX mode. This is wrong if you want to check TeX syntax. However, parentheses and square brackets are likely to be used in text as matching delimiters and it is useful for the various motion commands and automatic match display to work with them. In LaTeX input, `\begin' and `\end' commands must balance. After you insert a `\begin', use `C-c C-f' (`tex-close-latex-block') to insert automatically a matching `\end' (on a new line following the `\begin'). A blank line is inserted between the two, and point is left there. File: xemacs.info, Node: TeX Print, Prev: TeX Editing, Up: TeX Mode TeX Printing Commands ..................... You can invoke TeX as an inferior of Emacs on either the entire contents of the buffer or just a region at a time. Running TeX in this way on just one chapter is a good way to see what your changes look like without taking the time to format the entire file. `C-c C-r' Invoke TeX on the current region, plus the buffer's header (`tex-region'). `C-c C-b' Invoke TeX on the entire current buffer (`tex-buffer'). `C-c C-l' Recenter the window showing output from the inferior TeX so that the last line can be seen (`tex-recenter-output-buffer'). `C-c C-k' Kill the inferior TeX (`tex-kill-job'). `C-c C-p' Print the output from the last `C-c C-r' or `C-c C-b' command (`tex-print'). `C-c C-q' Show the printer queue (`tex-show-print-queue'). You can pass the current buffer through an inferior TeX using `C-c C-b' (`tex-buffer'). The formatted output appears in a file in `/tmp'; to print it, type `C-c C-p' (`tex-print'). Afterward use `C-c C-q' (`tex-show-print-queue') to view the progress of your output towards being printed. The console output from TeX, including any error messages, appears in a buffer called `*TeX-shell*'. If TeX gets an error, you can switch to this buffer and feed it input (this works as in Shell mode; *note Interactive Shell::.). Without switching to this buffer, you can scroll it so that its last line is visible by typing `C-c C-l'. Type `C-c C-k' (`tex-kill-job') to kill the TeX process if you see that its output is no longer useful. Using `C-c C-b' or `C-c C-r' also kills any TeX process still running. You can pass an arbitrary region through an inferior TeX by typing `C-c C-r' (`tex-region'). This is tricky, however, because most files of TeX input contain commands at the beginning to set parameters and define macros. Without them, no later part of the file will format correctly. To solve this problem, `C-c C-r' allows you to designate a part of the file as containing essential commands; it is included before the specified region as part of the input to TeX. The designated part of the file is called the "header". To indicate the bounds of the header in Plain TeX mode, insert two special strings in the file: `%**start of header' before the header, and `%**end of header' after it. Each string must appear entirely on one line, but there may be other text on the line before or after. The lines containing the two strings are included in the header. If `%**start of header' does not appear within the first 100 lines of the buffer, `C-c C-r' assumes there is no header. In LaTeX mode, the header begins with `\documentstyle' and ends with `\begin{document}'. These are commands that LaTeX requires you to use, so you don't need to do anything special to identify the header. When you enter either kind of TeX mode, Emacs calls with no arguments the value of the variable `text-mode-hook', if that value exists and is not `nil'. Emacs then calls the variable `TeX-mode-hook' and either `plain-TeX-mode-hook' or `LaTeX-mode-hook' under the same conditions. File: xemacs.info, Node: Outline Mode, Prev: TeX Mode, Up: Text Mode Outline Mode ------------ Outline mode is a major mode similar to Text mode but intended for editing outlines. It allows you to make parts of the text temporarily invisible so that you can see just the overall structure of the outline. Type `M-x outline-mode' to turn on Outline mode in the current buffer. When you enter Outline mode, Emacs calls with no arguments the value of the variable `text-mode-hook', if that value exists and is not `nil'; then it does the same with the variable `outline-mode-hook'. When a line is invisible in outline mode, it does not appear on the screen. The screen appears exactly as if the invisible line were deleted, except that an ellipsis (three periods in a row) appears at the end of the previous visible line (only one ellipsis no matter how many invisible lines follow). All editing commands treat the text of the invisible line as part of the previous visible line. For example, `C-n' moves onto the next visible line. Killing an entire visible line, including its terminating newline, really kills all the following invisible lines as well; yanking everything back yanks the invisible lines and they remain invisible. * Menu: * Format: Outline Format. What the text of an outline looks like. * Motion: Outline Motion. Special commands for moving through outlines. * Visibility: Outline Visibility. Commands to control what is visible. File: xemacs.info, Node: Outline Format, Next: Outline Motion, Prev: Outline Mode, Up: Outline Mode Format of Outlines .................. Outline mode assumes that the lines in the buffer are of two types: "heading lines" and "body lines". A heading line represents a topic in the outline. Heading lines start with one or more stars; the number of stars determines the depth of the heading in the outline structure. Thus, a heading line with one star is a major topic; all the heading lines with two stars between it and the next one-star heading are its subtopics; and so on. Any line that is not a heading line is a body line. Body lines belong to the preceding heading line. Here is an example: * Food This is the body, which says something about the topic of food. ** Delicious Food This is the body of the second-level header. ** Distasteful Food This could have a body too, with several lines. *** Dormitory Food * Shelter A second first-level topic with its header line. A heading line together with all following body lines is called collectively an "entry". A heading line together with all following deeper heading lines and their body lines is called a "subtree". You can customize the criterion for distinguishing heading lines by setting the variable `outline-regexp'. Any line whose beginning has a match for this regexp is considered a heading line. Matches that start within a line (not at the beginning) do not count. The length of the matching text determines the level of the heading; longer matches make a more deeply nested level. Thus, for example, if a text formatter has commands `@chapter', `@section' and `@subsection' to divide the document into chapters and sections, you can make those lines count as heading lines by setting `outline-regexp' to `"@chap\\|@\$sub\$*section"'. Note the trick: the two words `chapter' and `section' are the same length, but by defining the regexp to match only `chap' we ensure that the length of the text matched on a chapter heading is shorter, so that Outline mode will know that sections are contained in chapters. This works as long as no other command starts with `@chap'. Outline mode makes a line invisible by changing the newline before it into an ASCII Control-M (code 015). Most editing commands that work on lines treat an invisible line as part of the previous line because, strictly speaking, it is part of that line, since there is no longer a newline in between. When you save the file in Outline mode, Control-M characters are saved as newlines, so the invisible lines become ordinary lines in the file. Saving does not change the visibility status of a line inside Emacs. File: xemacs.info, Node: Outline Motion, Next: Outline Visibility, Prev: Outline Format, Up: Outline Mode Outline Motion Commands ....................... Some special commands in Outline mode move backward and forward to heading lines. `C-c C-n' Move point to the next visible heading line (`outline-next-visible-heading'). `C-c C-p' Move point to the previous visible heading line (`outline-previous-visible-heading'). `C-c C-f' Move point to the next visible heading line at the same level as the one point is on (`outline-forward-same-level'). `C-c C-b' Move point to the previous visible heading line at the same level (`outline-backward-same-level'). `C-c C-u' Move point up to a lower-level (more inclusive) visible heading line (`outline-up-heading'). `C-c C-n' (`next-visible-heading') moves down to the next heading line. `C-c C-p' (`previous-visible-heading') moves similarly backward. Both accept numeric arguments as repeat counts. The names emphasize that invisible headings are skipped, but this is not really a special feature. All editing commands that look for lines ignore the invisible lines automatically. More advanced motion commands understand the levels of headings. The commands `C-c C-f' (`outline-forward-same-level') and `C-c C-b' (`outline-backward-same-level') move from one heading line to another visible heading at the same depth in the outline. `C-c C-u' (`outline-up-heading') moves backward to another heading that is less deeply nested. File: xemacs.info, Node: Outline Visibility, Prev: Outline Motion, Up: Outline Mode Outline Visibility Commands ........................... The other special commands of outline mode are used to make lines visible or invisible. Their names all start with `hide' or `show'. Most of them exist as pairs of opposites. They are not undoable; instead, you can undo right past them. Making lines visible or invisible is simply not recorded by the undo mechanism. `M-x hide-body' Make all body lines in the buffer invisible. `M-x show-all' Make all lines in the buffer visible. `C-c C-d' Make everything under this heading invisible, not including this heading itself (`hide-subtree'). `C-c C-s' Make everything under this heading visible, including body, subheadings, and their bodies (`show-subtree'). `M-x hide-leaves' Make the body of this heading line, and of all its subheadings, invisible. `M-x show-branches' Make all subheadings of this heading line, at all levels, visible. `C-c C-i' Make immediate subheadings (one level down) of this heading line visible (`show-children'). `M-x hide-entry' Make this heading line's body invisible. `M-x show-entry' Make this heading line's body visible. Two commands that are exact opposites are `M-x hide-entry' and `M-x show-entry'. They are used with point on a heading line, and apply only to the body lines of that heading. The subtopics and their bodies are not affected. Two more powerful opposites are `C-c C-h' (`hide-subtree') and `C-c C-s' (`show-subtree'). Both should be used when point is on a heading line, and both apply to all the lines of that heading's "subtree": its body, all its subheadings, both direct and indirect, and all of their bodies. In other words, the subtree contains everything following this heading line, up to and not including the next heading of the same or higher rank. Intermediate between a visible subtree and an invisible one is having all the subheadings visible but none of the body. There are two commands for doing this, one that hides the bodies and one that makes the subheadings visible. They are `M-x hide-leaves' and `M-x show-branches'. A little weaker than `show-branches' is `C-c C-i' (`show-children'). It makes just the direct subheadings visible--those one level down. Deeper subheadings remain invisible. Two commands have a blanket effect on the whole file. `M-x hide-body' makes all body lines invisible, so that you see just the outline structure. `M-x show-all' makes all lines visible. You can think of these commands as a pair of opposites even though `M-x show-all' applies to more than just body lines. You can turn off the use of ellipses at the ends of visible lines by setting `selective-display-ellipses' to `nil'. The result is no visible indication of the presence of invisible lines. File: xemacs.info, Node: Words, Next: Sentences, Prev: Text Mode, Up: Text Words ===== Emacs has commands for moving over or operating on words. By convention, the keys for them are all `Meta-' characters. `M-f' Move forward over a word (`forward-word'). `M-b' Move backward over a word (`backward-word'). `M-d' Kill up to the end of a word (`kill-word'). `M-<DEL>' Kill back to the beginning of a word (`backward-kill-word'). `M-@' Mark the end of the next word (`mark-word'). `M-t' Transpose two words; drag a word forward or backward across other words (`transpose-words'). Notice how these keys form a series that parallels the character-based `C-f', `C-b', `C-d', `C-t' and <DEL>. `M-@' is related to `C-@', which is an alias for `C-<SPC>'. The commands `Meta-f' (`forward-word') and `Meta-b' (`backward-word') move forward and backward over words. They are analogous to `Control-f' and `Control-b', which move over single characters. Like their `Control-' analogues, `Meta-f' and `Meta-b' move several words if given an argument. `Meta-f' with a negative argument moves backward, and `Meta-b' with a negative argument moves forward. Forward motion stops after the last letter of the word, while backward motion stops before the first letter. `Meta-d' (`kill-word') kills the word after point. To be precise, it kills everything from point to the place `Meta-f' would move to. Thus, if point is in the middle of a word, `Meta-d' kills just the part after point. If some punctuation comes between point and the next word, it is killed along with the word. (To kill only the next word but not the punctuation before it, simply type `Meta-f' to get to the end and kill the word backwards with `Meta-<DEL>'.) `Meta-d' takes arguments just like `Meta-f'. `Meta-<DEL>' (`backward-kill-word') kills the word before point. It kills everything from point back to where `Meta-b' would move to. If point is after the space in `FOO, BAR', then `FOO, ' is killed. To kill just `FOO', type `Meta-b Meta-d' instead of `Meta-<DEL>'. `Meta-t' (`transpose-words') exchanges the word before or containing point with the following word. The delimiter characters between the words do not move. For example, transposing `FOO, BAR' results in `BAR, FOO' rather than `BAR FOO,'. *Note Transpose::, for more on transposition and on arguments to transposition commands. To operate on the next N words with an operation which applies between point and mark, you can either set the mark at point and then move over the words, or you can use the command `Meta-@' (`mark-word') which does not move point but sets the mark where `Meta-f' would move to. It can be given arguments just like `Meta-f'. The word commands' understanding of syntax is completely controlled by the syntax table. For example, any character can be declared to be a word delimiter. *Note Syntax::. File: xemacs.info, Node: Sentences, Next: Paragraphs, Prev: Words, Up: Text Sentences ========= The Emacs commands for manipulating sentences and paragraphs are mostly on `Meta-' keys, and therefore are like the word-handling commands. `M-a' Move back to the beginning of the sentence (`backward-sentence'). `M-e' Move forward to the end of the sentence (`forward-sentence'). `M-k' Kill forward to the end of the sentence (`kill-sentence'). `C-x <DEL>' Kill back to the beginning of the sentence (`backward-kill-sentence'). The commands `Meta-a' and `Meta-e' (`backward-sentence' and `forward-sentence') move to the beginning and end of the current sentence, respectively. They resemble `Control-a' and `Control-e', which move to the beginning and end of a line. Unlike their counterparts, `Meta-a' and `Meta-e' move over successive sentences if repeated or given numeric arguments. Emacs assumes the typist's convention is followed, and thus considers a sentence to end wherever there is a `.', `?', or `!' followed by the end of a line or two spaces, with any number of `)', `]', `'', or `"' characters allowed in between. A sentence also begins or ends wherever a paragraph begins or ends. Neither `M-a' nor `M-e' moves past the newline or spaces beyond the sentence edge at which it is stopping. `M-a' and `M-e' have a corresponding kill command, just like `C-a' and `C-e' have `C-k'. The command is `M-k' (`kill-sentence') which kills from point to the end of the sentence. With minus one as an argument it kills back to the beginning of the sentence. Larger arguments serve as repeat counts. There is a special command, `C-x <DEL>' (`backward-kill-sentence'), for killing back to the beginning of a sentence, which is useful when you change your mind in the middle of composing text. The variable `sentence-end' controls recognition of the end of a sentence. It is a regexp that matches the last few characters of a sentence, together with the whitespace following the sentence. Its normal value is: "[.?!][]\"')]*\$$\\|\t\\| \$[ \t\n]*" This example is explained in the section on regexps. *Note Regexps::. File: xemacs.info, Node: Paragraphs, Next: Pages, Prev: Sentences, Up: Text Paragraphs ========== The Emacs commands for manipulating paragraphs are also `Meta-' keys. `M-[' Move back to previous paragraph beginning (`backward-paragraph'). `M-]' Move forward to next paragraph end (`forward-paragraph'). `M-h' Put point and mark around this or next paragraph (`mark-paragraph'). `Meta-[' moves to the beginning of the current or previous paragraph, while `Meta-]' moves to the end of the current or next paragraph. Blank lines and text formatter command lines separate paragraphs and are not part of any paragraph. An indented line starts a new paragraph. In major modes for programs (as opposed to Text mode), paragraphs begin and end only at blank lines. As a result, the paragraph commands continue to be useful even though there are no paragraphs per se. When there is a fill prefix, paragraphs are delimited by all lines which don't start with the fill prefix. *Note Filling::. To operate on a paragraph, you can use the command `Meta-h' (`mark-paragraph') to set the region around it. This command puts point at the beginning and mark at the end of the paragraph point was in. If point is between paragraphs (in a run of blank lines or at a boundary), the paragraph following point is surrounded by point and mark. If there are blank lines preceding the first line of the paragraph, one of the blank lines is included in the region. Thus, for example, `M-h C-w' kills the paragraph around or after point. The precise definition of a paragraph boundary is controlled by the variables `paragraph-separate' and `paragraph-start'. The value of `paragraph-start' is a regexp that matches any line that either starts or separates paragraphs. The value of `paragraph-separate' is another regexp that matches only lines that separate paragraphs without being part of any paragraph. Lines that start a new paragraph and are contained in it must match both regexps. For example, normally `paragraph-start' is `"^[ \t\n\f]"' and `paragraph-separate' is `"^[ \t\f]*$"'. Normally it is desirable for page boundaries to separate paragraphs. The default values of these variables recognize the usual separator for pages. File: xemacs.info, Node: Pages, Next: Filling, Prev: Paragraphs, Up: Text Pages ===== Files are often thought of as divided into "pages" by the "formfeed" character (ASCII Control-L, octal code 014). For example, if a file is printed on a line printer, each "page" of the file starts on a new page of paper. Emacs treats a page-separator character just like any other character. It can be inserted with `C-q C-l' or deleted with <DEL>. You are free to paginate your file or not. However, since pages are often meaningful divisions of the file, commands are provided to move over them and operate on them. `C-x [' Move point to previous page boundary (`backward-page'). `C-x ]' Move point to next page boundary (`forward-page'). `C-x C-p' Put point and mark around this page (or another page) (`mark-page'). `C-x l' Count the lines in this page (`count-lines-page'). The `C-x [' (`backward-page') command moves point to immediately after the previous page delimiter. If point is already right after a page delimiter, the command skips that one and stops at the previous one. A numeric argument serves as a repeat count. The `C-x ]' (`forward-page') command moves forward past the next page delimiter. The `C-x C-p' command (`mark-page') puts point at the beginning of the current page and the mark at the end. The page delimiter at the end is included (the mark follows it). The page delimiter at the front is excluded (point follows it). You can follow this command by `C-w' to kill a page you want to move elsewhere. If you insert the page after a page delimiter, at a place where `C-x ]' or `C-x [' would take you, the page will be properly delimited before and after once again. A numeric argument to `C-x C-p' is used to specify which page to go to, relative to the current one. Zero means the current page. One means the next page, and -1 means the previous one. The `C-x l' command (`count-lines-page') can help you decide where to break a page in two. It prints the total number of lines in the current page in the echo area, then divides the lines into those preceding the current line and those following it, for example Page has 96 (72+25) lines Notice that the sum is off by one; this is correct if point is not at the beginning of a line. The variable `page-delimiter' should have as its value a regexp that matches the beginning of a line that separates pages. This defines where pages begin. The normal value of this variable is `"^\f"', which matches a formfeed character at the beginning of a line. File: xemacs.info, Node: Filling, Next: Case, Prev: Pages, Up: Text Filling Text ============ If you use Auto Fill mode, Emacs "fills" text (breaks it up into lines that fit in a specified width) as you insert it. When you alter existing text it is often no longer be properly filled afterwards and you can use explicit commands for filling. * Menu: * Auto Fill:: Auto Fill mode breaks long lines automatically. * Fill Commands:: Commands to refill paragraphs and center lines. * Fill Prefix:: Filling when every line is indented or in a comment, etc. File: xemacs.info, Node: Auto Fill, Next: Fill Commands, Prev: Filling, Up: Filling Auto Fill Mode -------------- "Auto Fill" mode is a minor mode in which lines are broken automatically when they become too wide. Breaking happens only when you type a <SPC> or <RET>. `M-x auto-fill-mode' Enable or disable Auto Fill mode. `<SPC>' `<RET>' In Auto Fill mode, break lines when appropriate. `M-x auto-fill-mode' turns Auto Fill mode on if it was off, or off if it was on. With a positive numeric argument the command always turns Auto Fill mode on, and with a negative argument it always turns it off. The presence of the word `Fill' in the mode line, inside the parentheses, indicates that Auto Fill mode is in effect. Auto Fill mode is a minor mode; you can turn it on or off for each buffer individually. *Note Minor Modes::. In Auto Fill mode, lines are broken automatically at spaces when they get longer than desired. Line breaking and rearrangement takes place only when you type <SPC> or <RET>. To insert a space or newline without permitting line-breaking, type `C-q <SPC>' or `C-q <LFD>' (recall that a newline is really a linefeed). `C-o' inserts a newline without line breaking. Auto Fill mode works well with Lisp mode: when it makes a new line in Lisp mode, it indents that line with <TAB>. If a line ending in a Lisp comment gets too long, the text of the comment is split into two comment lines. Optionally, new comment delimiters are inserted at the end of the first line and the beginning of the second, so that each line is a separate comment. The variable `comment-multi-line' controls the choice (*note Comments::.). Auto Fill mode does not refill entire paragraphs. It can break lines but cannot merge lines. Editing in the middle of a paragraph can result in a paragraph that is not correctly filled. The easiest way to make the paragraph properly filled again is using an explicit fill commands. Many users like Auto Fill mode and want to use it in all text files. The section on init files explains how you can arrange this permanently for yourself. *Note Init File::. File: xemacs.info, Node: Fill Commands, Next: Fill Prefix, Prev: Auto Fill, Up: Filling Explicit Fill Commands ---------------------- `M-q' Fill current paragraph (`fill-paragraph'). `M-g' Fill each paragraph in the region (`fill-region'). `C-x f' Set the fill column (`set-fill-column'). `M-x fill-region-as-paragraph' Fill the region, considering it as one paragraph. `M-s' Center a line. To refill a paragraph, use the command `Meta-q' (`fill-paragraph'). It causes the paragraph containing point, or the one after point if point is between paragraphs, to be refilled. All line breaks are removed, and new ones are inserted where necessary. `M-q' can be undone with `C-_'. *Note Undo::. To refill many paragraphs, use `M-g' (`fill-region'), which divides the region into paragraphs and fills each of them. `Meta-q' and `Meta-g' use the same criteria as `Meta-h' for finding paragraph boundaries (*note Paragraphs::.). For more control, you can use `M-x fill-region-as-paragraph', which refills everything between point and mark. This command recognizes only blank lines as paragraph separators. A numeric argument to `M-g' or `M-q' causes it to "justify" the text as well as filling it. Extra spaces are inserted to make the right margin line up exactly at the fill column. To remove the extra spaces, use `M-q' or `M-g' with no argument. The variable `auto-fill-inhibit-regexp' takes as a value a regexp to match lines that should not be auto-filled. The command `Meta-s' (`center-line') centers the current line within the current fill column. With an argument, it centers several lines individually and moves past them. The maximum line width for filling is in the variable `fill-column'. Altering the value of `fill-column' makes it local to the current buffer; until then, the default value--initially 70--is in effect. *Note Locals::. The easiest way to set `fill-column' is to use the command `C-x f' (`set-fill-column'). With no argument, it sets `fill-column' to the current horizontal position of point. With a numeric argument, it uses that number as the new fill column. File: xemacs.info, Node: Fill Prefix, Prev: Fill Commands, Up: Filling The Fill Prefix --------------- To fill a paragraph in which each line starts with a special marker (which might be a few spaces, giving an indented paragraph), use the "fill prefix" feature. The fill prefix is a string which is not included in filling. Emacs expects every line to start with a fill prefix. `C-x .' Set the fill prefix (`set-fill-prefix'). `M-q' Fill a paragraph using current fill prefix (`fill-paragraph'). `M-x fill-individual-paragraphs' Fill the region, considering each change of indentation as starting a new paragraph. To specify a fill prefix, move to a line that starts with the desired prefix, put point at the end of the prefix, and give the command `C-x .' (`set-fill-prefix'). That's a period after the `C-x'. To turn off the fill prefix, specify an empty prefix: type `C-x .' with point at the beginning of a line. When a fill prefix is in effect, the fill commands remove the fill prefix from each line before filling and insert it on each line after filling. Auto Fill mode also inserts the fill prefix inserted on new lines it creates. Lines that do not start with the fill prefix are considered to start paragraphs, both in `M-q' and the paragraph commands; this is just right if you are using paragraphs with hanging indentation (every line indented except the first one). Lines which are blank or indented once the prefix is removed also separate or start paragraphs; this is what you want if you are writing multi-paragraph comments with a comment delimiter on each line. The fill prefix is stored in the variable `fill-prefix'. Its value is a string, or `nil' when there is no fill prefix. This is a per-buffer variable; altering the variable affects only the current buffer, but there is a default value which you can change as well. *Note Locals::. Another way to use fill prefixes is through `M-x fill-individual-paragraphs'. This function divides the region into groups of consecutive lines with the same amount and kind of indentation and fills each group as a paragraph, using its indentation as a fill prefix. File: xemacs.info, Node: Case, Prev: Filling, Up: Text Case Conversion Commands ======================== Emacs has commands for converting either a single word or any arbitrary range of text to upper case or to lower case. `M-l' Convert following word to lower case (`downcase-word'). `M-u' Convert following word to upper case (`upcase-word'). `M-c' Capitalize the following word (`capitalize-word'). `C-x C-l' Convert region to lower case (`downcase-region'). `C-x C-u' Convert region to upper case (`upcase-region'). The word conversion commands are used most frequently. `Meta-l' (`downcase-word') converts the word after point to lower case, moving past it. Thus, repeating `Meta-l' converts successive words. `Meta-u' (`upcase-word') converts to all capitals instead, while `Meta-c' (`capitalize-word') puts the first letter of the word into upper case and the rest into lower case. The word conversion commands convert several words at once if given an argument. They are especially convenient for converting a large amount of text from all upper case to mixed case: you can move through the text using `M-l', `M-u', or `M-c' on each word as appropriate, occasionally using `M-f' instead to skip a word. When given a negative argument, the word case conversion commands apply to the appropriate number of words before point, but do not move point. This is convenient when you have just typed a word in the wrong case: you can give the case conversion command and continue typing. If a word case conversion command is given in the middle of a word, it applies only to the part of the word which follows point. This is just like what `Meta-d' (`kill-word') does. With a negative argument, case conversion applies only to the part of the word before point. The other case conversion commands are `C-x C-u' (`upcase-region') and `C-x C-l' (`downcase-region'), which convert everything between point and mark to the specified case. Point and mark do not move. File: xemacs.info, Node: Programs, Next: Running, Prev: Text, Up: Top Editing Programs **************** Emacs has many commands designed to understand the syntax of programming languages such as Lisp and C. These commands can: * Move over or kill balanced expressions or "sexps" (*note Lists::.). * Move over or mark top-level balanced expressions ("defuns", in Lisp; functions, in C). * Show how parentheses balance (*note Matching::.). * Insert, kill, or align comments (*note Comments::.). * Follow the usual indentation conventions of the language (*note Grinding::.). The commands available for words, sentences, and paragraphs are useful in editing code even though their canonical application is for editing human language text. Most symbols contain words (*note Words::.); sentences can be found in strings and comments (*note Sentences::.). Paragraphs per se are not present in code, but the paragraph commands are useful anyway, because Lisp mode and C mode define paragraphs to begin and end at blank lines (*note Paragraphs::.). Judicious use of blank lines to make the program clearer also provides interesting chunks of text for the paragraph commands to work on. The selective display feature is useful for looking at the overall structure of a function (*note Selective Display::.). This feature causes only the lines that are indented less than a specified amount to appear on the screen. * Menu: * Program Modes:: Major modes for editing programs. * Lists:: Expressions with balanced parentheses. There are editing commands to operate on them. * Defuns:: Each program is made up of separate functions. There are editing commands to operate on them. * Grinding:: Adjusting indentation to show the nesting. * Matching:: Insertion of a close-delimiter flashes matching open. * Comments:: Inserting, illing and aligning comments. * Balanced Editing:: Inserting two matching parentheses at once, etc. * Lisp Completion:: Completion on symbol names in Lisp code. * Documentation:: Getting documentation of functions you plan to call. * Change Log:: Maintaining a change history for your program. * Tags:: Go direct to any function in your program in one command. Tags remembers which file it is in. * Fortran:: Fortran mode and its special features. * Asm Mode:: Asm mode and its special features. File: xemacs.info, Node: Program Modes, Next: Lists, Prev: Programs, Up: Programs Major Modes for Programming Languages ===================================== Emacs has several major modes for the programming languages Lisp, Scheme (a variant of Lisp), C, Fortran, and Muddle. Ideally, a major mode should be implemented for each programming language you might want to edit with Emacs; but often the mode for one language can serve for other syntactically similar languages. The language modes that exist are those that someone decided to take the trouble to write. There are several variants of Lisp mode, which differ in the way they interface to Lisp execution. *Note Lisp Modes::. Each of the programming language modes defines the <TAB> key to run an indentation function that knows the indentation conventions of that language and updates the current line's indentation accordingly. For example, in C mode <TAB> is bound to `c-indent-line'. <LFD> is normally defined to do <RET> followed by <TAB>; thus it, too, indents in a mode-specific fashion. In most programming languages, indentation is likely to vary from line to line. So the major modes for those languages rebind <DEL> to treat a tab as if it were the equivalent number of spaces (using the command `backward-delete-char-untabify'). This makes it possible to rub out indentation one column at a time without worrying whether it is made up of spaces or tabs. In these modes, use `C-b C-d' to delete a tab character before point. Programming language modes define paragraphs to be separated only by blank lines, so that the paragraph commands remain useful. Auto Fill mode, if enabled in a programming language major mode, indents the new lines which it creates. Turning on a major mode calls a user-supplied function called the "mode hook", which is the value of a Lisp variable. For example, turning on C mode calls the value of the variable `c-mode-hook' if that value exists and is non-`nil'. Mode hook variables for other programming language modes include `lisp-mode-hook', `emacs-lisp-mode-hook', `lisp-interaction-mode-hook', `scheme-mode-hook', and `muddle-mode-hook'. The mode hook function receives no arguments.